Skip to content

OCPBUGS-56438: Update to Kubernetes v1.31.9 #29871

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-bot merged 2 commits into from
Jun 10, 2025
Merged

OCPBUGS-56438: Update to Kubernetes v1.31.9 #29871

openshift-merge-bot merged 2 commits into from
Jun 10, 2025

Conversation

@atiratree
Copy link
Member

@atiratree atiratree commented May 30, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 30, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 30, 2025

@atiratree: This pull request references Jira Issue OCPBUGS-56438, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from deads2k and sdodson May 30, 2025 09:13
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label May 30, 2025
@sdodson
Copy link
Member

sdodson commented May 30, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 30, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 30, 2025

@sdodson: This pull request references Jira Issue OCPBUGS-56438, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-56437 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-56437 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @wangke19

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sdodson
Copy link
Member

sdodson commented May 30, 2025

/retest-required

@openshift-ci openshift-ci bot requested a review from wangke19 May 30, 2025 13:32
bertinatto
bertinatto reviewed Jun 4, 2025
View reviewed changes
Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, bertinatto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 4, 2025
@bertinatto
Copy link
Member

bertinatto commented Jun 4, 2025

/label backport-risk-assessed
/hold
for #29889

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2025

@bertinatto: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

Details

In response to this:

/label backport-risk-assessed
/hold
for #29889

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@bertinatto
Copy link
Member

bertinatto commented Jun 6, 2025

/label backport-risk-assessed /hold for #29889

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 6, 2025
@bertinatto
Copy link
Member

bertinatto commented Jun 6, 2025

/label backport-risk-assessed

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2025

@bertinatto: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

Details

In response to this:

/label backport-risk-assessed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sdodson sdodson added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jun 6, 2025
@bertinatto
Copy link
Member

bertinatto commented Jun 6, 2025

/retest-required

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 6, 2025

/retest-required

Remaining retests: 0 against base HEAD 2b9bae9 and 2 for PR HEAD 7797472 in total

@wangke19
Copy link
Contributor

wangke19 commented Jun 9, 2025

/retest

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 9, 2025

/retest-required

Remaining retests: 0 against base HEAD 2b9bae9 and 2 for PR HEAD 7797472 in total

@sdodson sdodson mentioned this pull request Jun 9, 2025
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 9, 2025

/retest-required

Remaining retests: 0 against base HEAD 2b9bae9 and 2 for PR HEAD 7797472 in total

@bertinatto
Copy link
Member

bertinatto commented Jun 9, 2025

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 10, 2025 •
edited
Loading

@atiratree: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node-upgrade 7797472 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node 7797472 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn 7797472 link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-serial 7797472 link false /test e2e-aws-ovn-single-node-serial
ci/prow/okd-scos-e2e-aws-ovn 7797472 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 10, 2025

/retest-required

Remaining retests: 0 against base HEAD 2b9bae9 and 2 for PR HEAD 7797472 in total

@openshift-merge-bot openshift-merge-bot bot merged commit 9ea4f56 into openshift:release-4.18 Jun 10, 2025
23 of 28 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 10, 2025

@atiratree: Jira Issue OCPBUGS-56438: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-56438 has been moved to the MODIFIED state.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

openshift-bot commented Jun 10, 2025

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.18.0-202506101934.p0.g9ea4f56.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@sdodson sdodson Awaiting requested review from sdodson

@wangke19 wangke19 Awaiting requested review from wangke19

1 more reviewer

@bertinatto bertinatto bertinatto left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@dgoodwin dgoodwin

@bertinatto bertinatto

@adambkaplan adambkaplan

@kasturinarra kasturinarra

@Moebasim Moebasim

@jadhaj jadhaj

@pamoedom pamoedom

@prietyc123 prietyc123

@gangwgr gangwgr

@prabhapa prabhapa

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.